Compact networking device for remote stations

ABSTRACT

A tower-mounted networking device facilitates deploying a remote station without having to build a custom station aside a radio tower. The networking device&#39;s chassis comprises a mounting bracket, which includes a curved contour for mounting the networking device on the radio tower. Also, the chassis can be resistant to weather intrusion, by not including a vent, to allow the networking device to be installed outdoors. The networking device can include a first power port coupled to an external connection line from a source external to the tower, such that the external connection line provides at least power to the networking device. The networking device can use the power to power a set of antenna mounted on the radio tower. The networking device can also relay a network connection between a pair of antennas, and/or between an antenna and a network connection to an Internet service provider.

RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.15/959,031, titled “Compact Networking Device for Remote Stations,” byinventors Carlos E. Hernandez and Tianshu Chen, filed 20 Apr. 2018,which is a continuation of U.S. Pat. No. 9,980,017, titled “CompactNetworking Device for Remote Stations,” by inventors Carlos E. Hernandezand Tianshu Chen, issued 22 May 2018, which claims the benefit of U.S.Provisional Application No. 62/096,711, titled “Compact NetworkingDevice For Remote Stations,” by inventors Carlos E. Hernandez andTianshu Chen, filed 24 Dec. 2014, the disclosures of which areincorporated herein in their entirety.

BACKGROUND Field

This disclosure is generally related to remote stations for wirelesscomputer networks. More specifically, this disclosure is related to acompact networking device that can be easily mounted on a radio tower orat other a hard-to-reach locations.

Related Art

Cellular networks are typically realized using point-to-multipointradios mounted on a radio tower, driven by a base station set up at thebase of the tower. Also, some Internet service providers (ISPs) provideInternet connectivity to remote locations by installing radio towersthat use point-to-point antennas to relay the network connection to theremote location. Some radio towers include both point-to-point andpoint-to-multipoint radios that are driven by a ground-level basestation at the base of the tower.

Oftentimes, these base stations are put together using existingnetworking components that are configured to work together to achieve adesired goal. These components typically include routers, switches,power supplies, and server computers that are installed on a server rackand enclosed in a metal cabinet with ventilation. Deploying a remotestation is a tedious job that requires a technician to select whichcomponents to install into the cabinet, and to decide how to configureeach of these components.

In many cases, it can be difficult and time consuming for a technicianto maintain these remote stations. This is because the technician mayneed to connect to each individual component installed in the cabinet todetermine its status, and to diagnose any potential problems. To makematters worse, service providers may change the strategy they use to setup these remote stations over time, which results in their remotestations having different configurations from each other.

Unfortunately, this results in non-homogenous remote stations that eachhas a different set of hardware or software components, and each needsto be monitored or controlled in a different way. This non-homogenousnature can cause a technician valuable time in servicing a remotestation deployed using equipment that the technician has little or noexperience with, as it can require the technician to first decipher howthe remote station has been set up before he can even determine what hecan do to service or repair the remote station.

SUMMARY

One embodiment provides a tower-mounted computer networking deviceapparatus that facilitates deploying a remote station without having tobuild a custom station aside a radio tower. The networking device'schassis comprises a mounting bracket, which includes a curved contourfor mounting the networking device on an antenna tower. Also, thechassis can be resistant to weather intrusion, by not including a vent,to allow the networking device to be installed outdoors. The networkingdevice can include a first power port coupled to an external connectionline from a source external to the tower, such that the externalconnection line provides at least power to the networking device. Thenetworking device also includes a second network port coupled to a firstradio transceiver, and a third network port coupled to a second radiotransceiver.

In some embodiments, the radio device includes a radio transmitter, aradio receiver, and/or a radio transceiver.

In some embodiments, the networking device includes a power module toreceive power from the first network port, provide power to the firstradio transceiver via the second network port, and provide power to thesecond radio transceiver via the third network port. The networkingdevice also includes a packet-forwarding module to route network packetsbetween the second network port and the third network port.

In some embodiments, the external connection line originates from one ormore of a ground-level power source, a ground-level telecommunicationsline, an overhead power line, and an overhead telecommunications line.

In some embodiments, the first power port is a network port, and theexternal connection line does not include a network connection.

In some embodiments, the first power port is a network port, and theexternal connection line includes a network connection. Moreover, thepacket-forwarding module can also route network packets between thefirst network port and the second network port, and can route networkpackets between the first network port and the third network port.

In some embodiments, the networking device can include a second powerport coupled to a power line from a solar panel mounted on the tower.

In some variations on these embodiments, the first power port is aprimary power source, and the second power port is a secondary powersource.

In some further variations on these embodiments, the power module candetermine whether the primary power source is active. Also, responsiveto determining that the primary power source is not active, the powermodule can receive power from the secondary power source.

In some embodiments, the mounting bracket also includes a set of screwholes for mounting the networking device on a flat surface.

In some embodiments, the networking device also includes a patch panelon a front face of the networking device, such that the patch panelincludes at least the first and second network ports. The networkingdevice also includes a panel cover comprising a locking mechanism that,when the panel cover is installed over the patch panel, the lockingmechanism penetrates through a chassis of the networking device to arear face of the networking device.

In some variations on these embodiments, the locking mechanism includesa lock hole for a lock, such that attaching a lock through the lock holesecures the panel cover to the patch panel.

In some embodiments, the networking device can include a motherboardcomprising two or more heat sources, and can include a heat sink. Thenetworking device can also include two or more heat pipes, such that arespective heat pipe is coupled to a corresponding heat source at oneend, and the two or more heat pipes are coupled to the same heat sink atan opposing end.

In some embodiments, the two or more heat sources can include acommunications microchip, a microprocessor, a power transistor, and asignal-amplifying microchip.

In some variations on these embodiments, a rear face of the chassisincludes a set of heat fins that are in thermal contact with the heatsink.

In some variations on these embodiments, the set of heat fins do notinclude a vent.

In some variations on these embodiments, a front face of the chassisincludes a set of heat fins above the heat sink.

In some variations on these embodiments, the set of heat fins do notinclude a vent.

One embodiment provides a computer networking device apparatus thatreceives power via a Power-over-Ethernet cable or a Power-over-Fibercable. The networking device includes a mounting bracket, which includesa curved contour for mounting the networking device on an antenna tower.The networking device can also include a first network port coupled to aconnection line from a source external to the tower, such that theconnection line provides to the networking device at least power, and anetwork connection. The networking device can also include a secondnetwork port coupled to a radio transceiver.

In some embodiments, the networking device can include a power module toreceive power from the first network port, and provide power to thefirst radio transceiver via the second network port. The networkingdevice can also include a packet-forwarding module to route networkpackets between the first network port and the second network port.

In some embodiments, the first network port is a Power-over-Ethernet(PoE) network port, and/or a Power-over-Fiber network port.

In some embodiments, the second network port is a Power-over-Ethernet(PoE) port.

One embodiment provides a computer networking device apparatus that onlyreceives power from a ground line, and relays network signals betweenradio antennas mounted on a radio router. Specifically, the networkingdevice is not coupled to an external network connection line from asource external to the tower. The networking device can include amounting bracket, which includes a curved contour for mounting thenetworking device on the antenna tower. The networking device includes apower port coupled to a power line from a solar panel mounted on thetower, such that the power line provides power to the networking device.Also, the networking device includes a first network port coupled to afirst radio transceiver, and includes a second network port coupled to asecond radio transceiver.

In some embodiments, the networking device includes a power module toreceive power from the power port, provide power to the first radiotransceiver via the first network port, and provide power to the secondradio transceiver via the second network port. Also, the networkingdevice includes a packet-forwarding module to route network packetsbetween the first network port and the second network port.

In some embodiments, the power port is a Power-over-Ethernet (PoE)network port, and/or a Power-over-Fiber network port.

One embodiment provides a cloud-based controller that facilitatesmonitoring and/or configuring a plurality of networking devices deployedover a wide geographic region. During operation, the controller canreceive a request, from a client device, to monitor one or morenetworking devices. The controller determines a location for the one ormore tower-mounted networking devices, and determining a set oftransceivers coupled to a respective networking device. The controllercan generate a user interface which overlays device icons for the one ormore networking devices over a geographic region, based on a geographiclocation for the one or more networking devices. A device icon for arespective networking device illustrates at least a signal strengthassociated with the respective networking device.

In some embodiments, the status can include a network throughput for apredetermined network port, a signal strength for a predeterminedtransceiver, an aggregate signal strength for one or more transceivers,and/or an average signal strength for one or more transceivers.

In some embodiments, responsive to receiving a user selection for therespective networking device, the controller can update the userinterface to present detailed information on the respective networkingdevice.

In some embodiments, the detailed information can include aconfiguration for one or more components of the networking device, anoperating state for the one or more components of the networking device,an alert associated with a misconfigured or underperforming componentsof the networking device, and/or a diagnosis associated with the alert.

In some embodiments, the controller can receive a device configurationfor a respective networking device, and configures the respectivenetworking device based on the received device configuration.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates a typical remote station realized using a radio towerwith a ground-level base station in accordance with an embodiment.

FIG. 2A illustrates a remote station that includes an exemplary radiotower with a tower-mounted networking device in accordance with anembodiment.

FIG. 2B illustrates a tower-mounted network device providing one powerand data connection to a transceiver on each antenna mounted on a radiotower in accordance with an embodiment.

FIG. 2C illustrates a tower-mounted network device providing one powerand data connection to each of multiple transceivers on one antenna inaccordance with an embodiment.

FIG. 3A illustrates a network device chassis in accordance with anembodiment.

FIG. 3B shows a front view of a network device chassis in accordancewith an embodiment.

FIG. 3C illustrates a side profile of a networking device in accordancewith an embodiment.

FIG. 4 illustrates an angled view of a networking device in accordancewith an embodiment.

FIG. 5A illustrates a plurality of terminals accessible via a patchpanel of a networking device in accordance with an embodiment.

FIG. 5B illustrates a conduit port and a conduit adapter of a networkingdevice in accordance with an embodiment.

FIG. 5C illustrates an exemplary cable sleeve in accordance with anembodiment.

FIG. 5D illustrates an exemplary cable sleeve with a gasket adhered to aconduit adapter in accordance with an embodiment.

FIG. 5E illustrates an exemplary cable sleeve coupled to a conduit portin accordance with an embodiment.

FIG. 5F illustrates an exemplary cable sleeve being wrapped or unwrappedfrom a set of cables in accordance with an embodiment.

FIG. 5G illustrates an exemplary conduit adapter 522 with a membrane 540at a distal end in accordance with an embodiment.

FIG. 6A illustrates a mounting bracket for a networking device 600 inaccordance with an embodiment.

FIG. 6B illustrates a set of rails on a networking device partiallyinserted into a mounting bracket in accordance with an embodiment.

FIG. 7 illustrates a set of cable-fastener loops on a compartmentsurface of a networking device in accordance with an embodiment.

FIG. 8 illustrates curved surfaces underneath cable-fastener loops ofnetworking device 800 in accordance with an embodiment.

FIG. 9A illustrates a networking device with a multiple heat pipeconfiguration in accordance with an embodiment.

FIG. 9B illustrates an angled side view of a heat pipes mounted on aheat sink in accordance with an embodiment.

FIG. 10 illustrates a networking device exposing a single heat pipeconfiguration in accordance with an embodiment.

FIG. 11 illustrates a set of heat-dissipating fins of a networkingdevice 1100 in accordance with an embodiment.

FIG. 12 illustrates a close-up angled view of heat-dissipating fins on arear surface of a networking device in accordance with an embodiment.

FIG. 13 illustrates a front-chassis for a low-power networking device inaccordance with an embodiment.

FIG. 14 illustrates a patch panel of a low-power networking device 1400in accordance with an embodiment.

FIG. 15 illustrates a pole-mount feature of a low-power networkingdevice 1500 in accordance with an embodiment.

FIG. 16 illustrates a curved contour of a pole-mount feature inaccordance with an embodiment.

FIG. 17 illustrates a PCB compartment of a low-power networking devicein accordance with an embodiment.

FIG. 18 illustrates a cover plate of a networking device in accordancewith an embodiment.

FIG. 19 illustrates an exemplary light pipe assembly of a networkingdevice in accordance with an embodiment.

FIG. 20 presents a flow chart illustrating a method for managing a setof networking devices from a remote cloud controller in accordance withan embodiment.

FIG. 21 illustrates an exemplary computer system that facilitatesmanaging a set of networking devices in accordance with an embodiment.

In the figures, like reference numerals refer to the same figureelements.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled inthe art to make and use the embodiments, and is provided in the contextof a particular application and its requirements. Various modificationsto the disclosed embodiments will be readily apparent to those skilledin the art, and the general principles defined herein may be applied toother embodiments and applications without departing from the spirit andscope of the present disclosure. Thus, the present invention is notlimited to the embodiments shown, but is to be accorded the widest scopeconsistent with the principles and features disclosed herein.

Overview

Embodiments of the present invention provide a networking device thatfacilitates deploying a remote station without having to build a customstation aside a radio tower. This networking device provides a unifiedstation that is easy to deploy, and provides a unified user interfacefor configuring the remote station's features. In some embodiments, thenetworking device can include a network switch, an edge router, a servercomputer, or any device deployed in a computer network.

Moreover, some networking devices (e.g., routers and switches) can bedeployed across multiple physical sites, which can make it easier forthe service provider (e.g., an Internet service provider, or ISP) tomanage these devices remotely or on-site. For example, the serviceprovider can access a cloud-based user interface (UI) that can remotelycontrol or configure a set of networking devices. Alternatively, theservice provider can access UI provided by the networking deviceon-site, such that this router-provided UI is uniform across all remotestations.

Deploying the networking device is more cost-effective for the providerthan deploying a custom remote station. This is because each remotestation device can cost less than the various separate components thatneed to be purchased to construct the custom remote station. Also,technicians may need less training to know how to configure or repairthe various remote station devices, and technicians may need to spendless time to manage the remote station devices (e.g., may need lesstechnicians).

In some embodiments, the networking device can have a small profile thatmay be easily lifted by one person, and can be easily affixed to a pole.These features make the networking device easier to install on top of anantenna tower along with one or more antennas. Being able to install thenetworking device atop a radio tower can make it less likely that thenetworking device will become damaged, be tampered with, or stolen by amalicious entity. It is currently not possible for service providers toinstall a remote station on top of a tower, given that remote stationsare typically installed in a large chassis that houses a multitude ofpower, computing, and networking components.

FIG. 1 illustrates a typical remote station 100 realized using a radiotower 102 with a ground-level base station 104 in accordance with anembodiment. Radio tower 102 can include one or more point-to-pointradios 106, and can include one or more cellular transceivers 108.Specifically, radios 106 and transceivers 108 are powered byground-level base station 104 via multiple external cables 110 thattravel from ground-level base station 104, up radio tower 102, and ontoeach radio 106 and transceiver 108. External cables 110 can include amultitude of cables, comprising at least a signal line for each radio,and a power line for each radio. The length of external cables 110 canaffect the service quality of radio tower 102 due to radio frequency(RF) interference, or tampering by malicious individuals or animals.

In some embodiments, a service provider may attempt to discourageunauthorized people from tampering with ground-level base station 104,radios 106, and/or transceivers 108 by surrounding radio tower 102 andground-level base station 104 by a security barrier (e.g., using a meshfence or using other security features). However, having to deploy asecurity barrier introduces additional costs and inefficiencies. Theservice provider needs to purchase and install these security barriersacross multiple remote stations 100. Also, if the security barrier is afence that includes a key lock, the service provider will also need toensure that the technicians have the appropriate keys to access eachremote station they are allowed to operate.

FIG. 2A illustrates a remote station 200 that includes an exemplaryradio tower 202 with a tower-mounted networking device 204 in accordancewith an embodiment. In some embodiments, networking device 204 providesa unified station that is simple, scalable, and easy to deploy.Networking device 204 includes a built-in mounting bracket which allowsnetworking device 204 to be mounted on a pole, or installed above groundeasily. This is not possible with typical rack-mount systems, whichrequire an external server rack to hold the off-the-shelf components.

For example, unlike typical remote stations whose networking componentsare installed at the floor level (and in easy reach of maliciousentities), networking device 204 can be installed high on radio tower202 or any other hard-to-reach location. Hence, radio tower 202 itselfcan be a security barrier that discourages malicious entities fromtampering with networking device 204. If one were to want to steal ortamper with tower-mounted networking device 204, that person would needto climb up radio tower 202, past any security barriers (e.g., asecurity barrier on radio tower 202), until that person reachesnetworking device 204, which is difficult to do. This difficulty inclimbing up to reach networking device 204 serves as an additionalsecurity feature that is not possible when using existing floor-levelremote stations.

Radio tower 202 can have multiple point-to-point radios 206 and/ortransceivers 208, pointing toward different directions and differentzones. For example, each antenna 206 may only cover a 60-degree area,and so radio tower 202 may include six antennas to cover a 360-degreeperimeter. Networking device 204 can also support multiplepoint-to-multipoint antennas, such as to provide Wi-Fi connections(e.g., via a Wi-Fi antenna) or cellular connections (e.g., via acellular antenna) to multiple devices.

In some embodiments, networking device 204 is itself resistant toweather intrusion, which also cuts on the costs of deploying a remotestation, as the service provider does not need to purchase an additionalweather-resistant cabinet to house networking equipment. Networkingdevice 204 can include high-power circuits for driving high-powerradios, and includes a chassis that successfully radiates heat away fromthese high-power circuits without requiring ventilation ports. Thisvent-less design allows networking device 204 to function in a varietyof weather conditions, such as rain, snow, wind, dust, etc.

In some embodiments, networking device 204 can also be deployed in anindoor environment, such as a stadium, a large mall, a casino, anairport, etc. If installed indoor, the low profile of networking device204 makes it easier to install behind a wall, so that only the antennais exposed to the open area. Also, if networking device 204 is installedout in the open, the low profile of networking device 204 is not avisual nuisance as a custom-built station that includes variouscomponents installed as a rack-mount system.

In some embodiments, antennas 206 and/or 208 may communicate using adifferent frequency to avoid interfering with each other. Networkingdevice 204 can make it easy to deploy such a system since the onlywiring needed is to connect each antenna 206 or 208 to a dedicated porton networking device 204, and connecting networking device 204 to a widearea network (WAN) and a power supply via a single external cable 212.The only wires that need to run down the pole of radio tower 202 are forthe power supply, and sometimes for a network connection.

In some embodiments, networking device 204 may only need to receive asingle external cable 212 that provides both the WAN connection andpower. Networking device 204 can provide power to antennas 206,transceivers 208, and/or other components mounted on tower 202 via a PoEconnection. For example, external cable 212 can include aPower-over-Ethernet (PoE) cable that provides a 24 V power line and anetwork connection via the Ethernet cable.

As another example, an ISP can provide a cable connection that providesan optical fiber for transferring data, as well as a separate connectionwithin the cable for providing electrical power. Networking device 204can receive the WAN connection and power via a single Power-over-Fiberexternal cable 212 that includes two fiber optic cables (e.g., for afull-duplex WAN connection), and includes a power line (e.g., a 24 V or50 V power line).

Alternatively, single external cable 212 may include both a PoEconnection and a fiber-optic connection. For example, the ISP mayprovide power via a PoE connection (e.g., a legacy connection), and mayprovide network connectivity via one or more separate fiber opticcables. As another variation, single external cable 212 may include adedicated power line for networking device 204, and may include one ormore network connections for networking device 204 (e.g., a fiber opticcable for fast connectivity, and an Ethernet cable for a backupconnectivity). As yet another variation, single external cable 212 caninclude multiple lines for power and/or network connections, andnetworking device 204 chooses (at runtime) which line provides thenecessary power and network connectivity.

In some embodiments, networking device 204 can be used to deploy apoint-to-point connection (e.g., using antennas 206). Hence, the onlywire that may need to be included in external cable 212 may be forpower. For example, radio tower 202 may be configured to function as arelay, where one antenna 206 provides a point-to-point connection to aremote upstream antenna (e.g., a WAN, or an ISP), and at least one otherlocal antenna 206 provides a point-to-point connection to a remotedownstream antenna (e.g., to a village, or to the next station). Radiotower 202 may include multiple antennas 206 that each relays the networkconnection to a different remote station. Radio tower 202 can includeadditional antennas or transceivers 208 that may provide a networkconnection to nearby devices, such as via a Wi-Fi or cellularconnection.

Networking device 204 is interoperable with different antennamanufacturers, and with different network equipment manufacturers.Hence, one radio tower 202 that is deployed with tower-mountednetworking device 204 can still interoperate with equipment on otherantenna towers, even if the other antenna tower uses an antenna with adifferent manufacturer or brand than the local antenna tower, or usesdifferent network equipment to provide power or network connection toits antenna. Networking device 204 can still manage the communicationbetween the two antenna towers.

In some embodiments, networking device 204 can provide a web-based UI,which allows a technician to configure networking device 204 withouthaving to climb up radio tower 202. The technician may access this UIlocally via a transceiver 208 mounted on radio tower 202, or via acloud-based service hosted on a distant server computer.

For example, if a network connection exists to networking device 204,the technician can configure networking device 204 via the networkconnection (e.g., via a WAN accessible via external cable 212, anantenna 206, or a transceiver 208). However, if the WAN networkconnection is down and networking device 204 is operational (e.g., haspower and is functional), the technician can configure networking device204 locally via a Wi-Fi or cellular transceiver 208 mounted on radiotower 202.

The technician can determine the status of a plurality of networkingdevices deployed over a wide area by using the cloud controller to pingeach networking device and determine its status. The cloud controllercan include a computer cluster that manages a plurality of networkingdevices for an entity (e.g., an ISP, or a company with a closednetwork), or for multiple entities. The cloud controller can getlocation information from each networking device, and can display thelocation of each networking device on a map, along with icons that eachrepresents a current status of a corresponding networking device. Thecloud controller can communicate with various networking devicesremotely to keep track of their status and configuration, and canpresent this diagnostic information to a technician via the cloud-basedUI so that the technician does not need to diagnose a radio towerin-person. If a networking device is malfunctioning or underperforming,the technician may decide to take down and replace the networking deviceas an easy fix.

In some embodiments, the cloud controller can also get diagnosticinformation from networking device 204 and present this diagnosticinformation to the technician on a map UI. The diagnostic informationcan include a configuration of networking device 204, performanceinformation (e.g., throughput information), information on the radios orantennas coupled to networking device 204, information on one or morepower sources, etc.

Presenting this diagnostic information for multiple radio towers to thetechnician in one unified user interface (UI) saves the technician timein keeping track of the various antennas and remote stations. This is asignificant advantage over existing remote stations, where it is notpossible to visualize the status of multiple remote stations in aunified UI, given that each remote station includes components fromdifferent manufacturers, and different remote stations may not havematching equipment. Hence, with existing systems, a technician wouldhave to manually ping each component of each remote station (e.g., eachswitch, each antenna, etc.) to determine its individual status. Thismakes it time consuming for the technician to debug a remote station, orto ensure that the remote station is operating normally.

The cloud-based UI can also provide a device-specific UI that displaysstatus information and configuration options for a given networkingdevice, such as which antennas are coupled to the networking device, thesignal quality and bandwidth of each antenna, etc. This device-specificUI allows the technician to perform a detailed analysis of a givennetworking device, for example, to determine whether a given radio towerneeds servicing, for example, to determine whether a given networkingdevice or antenna needs to be repaired or replaced.

Also, repairing or replacing networking device 204 is easier thandebugging a malfunctioning a custom remote station. For example, atechnician can upgrade, reconfigure, or debug a radio tower 202 byquickly replacing networking device 204 with another pre-configurednetworking device, and plugging antennas 206 and transceivers 208 to thenew networking device. In contrast, when a custom remote station isdeployed using existing components, one would need to first figure outwhich component of the base station is malfunctioning before anycomponents can be repaired or replaced. It is not always clear whichcomponent is malfunctioning or underperforming, given that the basestation may include a dedicated router, a dedicated switch, a localserver, etc.).

FIG. 2B illustrates a tower-mounted network device 234 providing onepower and data connection to a transceiver on each antenna mounted on aradio tower 232 in accordance with an embodiment. Network device 234 canitself receive power from an external cable 212, such as aPower-over-Fiber line that carries power and data over a long distance.Using Power-over-Fiber to provide power and data to a network device viaa single cable is described in U.S. patent application Ser. No.14/197,896 (entitled “Hybrid Fiber Optic and Power over Ethernet,” byinventors Ching-Yun Chien and Robert Pera, and filed 5 Mar. 2014), whichis hereby incorporated by reference.

Because antennas 236, 238, 240, and 242 are in close proximity tonetwork device 234, tower-mounted network device 234 can provide eachpower and data connection over a single Power-over-Ethernet (PoE) linethat exits from a conduit port at a bottom portion of network device234.

FIG. 2C illustrates a tower-mounted network device 234 providing onepower and data connection to each of multiple transceivers on oneantenna in accordance with an embodiment. Specifically, antenna 244 caninclude a set of four transceivers 246 that each may send and/or receivedata from a corresponding transceiver on a remote antenna. Usingmultiple transceivers on one antenna can effectively increase the datathroughput of the antenna, but typically requires running multiple dataand power lines up a tower. However, network device 234 can receive dataand power from a single external cable 212, and can provide power anddata to each transceiver on antenna 244 using a PoE line. The set of PoElines 248 can be grouped together, and passed into a connectioncompartment via a downward-facing conduit port.

Networking Device Design

FIG. 3A illustrates a chassis 300 for the networking device inaccordance with an embodiment. Specifically, chassis 300 can include afront chassis coupled to a rear chassis (not shown) to house aweather-resistant printed circuit board (PCB) chamber. For example,chassis 300 can include a set of fins 312 without a vent to dissipateheat away from high-power electronics of an internal PCB, whileprotecting the cable connectors and the internal electronics fromvarious environmental phenomenon such as rain, snow, dust, and sun heat.Also, a bottom-facing section of chassis 300 can include a port 304 forpassing a set of cables to a connector panel.

In some embodiments, this port can include a conduit port that can beused to couple a conduit (e.g., an electrical conduit) to chassis 300,such as to pass the cables to the connector panel via the conduit.Alternatively, a conduit adapter can be used to hold one end of a sleeveagainst port 304, so that the remainder of the sleeve can close a gapbetween the cables and port 304 to prevent various environmentalphenomenon from entering into the connector panel and/or the devicecircuitry.

FIG. 3B shows a front view of chassis 300 in accordance with anembodiment. Front chassis 300 includes a patch panel section 302 at abottom section of front chassis 300 to prevent water (e.g., rain) fromcoming in contact with and settling on a set of cable connectors. Frontchassis 300 also includes a set of heat-dissipating fins 312 near a topsection of front chassis 300 to dissipate heat that radiates upwardwithin the PCB chamber of the networking device. Front chassis 300 canalso include a set of light-emitting diodes (LEDs) 314 that eachindicates a status (e.g., a link status, a power status, etc.), andincludes a logo 316 (e.g., a manufacturer logo, a product logo, etc.).For example, LEDs 314 can be arranged in a column of LED pairs, where arespective LED pair indicates a transmit status and receive status for alink.

In some embodiments, heat-dissipating fins 312 may not include ventopenings that would dissipate air from inside of the networking device.Rather, heat-dissipating fins 312 include interdigitating sections ofsurface area that are elevated (or suppressed) relative to its twoneighboring sections of surface area. Hence, heat-dissipating fins 312provide additional surface area that improves the transfer of heat fromthe PCB chamber inside of networking device 300 to an environmentexternal to networking device 300.

FIG. 3C illustrates a side profile of the networking device 300 inaccordance with an embodiment. In some embodiments, the networkingdevice 300 can have a center of gravity near a mounting bracket 320affixed to networking device 300. Moreover, networking device 300 canhave a height-to-depth ratio within a range [3:1, 4:1]. In someembodiments, networking device 300 can have a height-to-depth ratio of13:4. This center of gravity near the mounting bracket, in combinationwith the narrow depth (relative to the height), for networking device300 can make it easier for a technician to handle while mountingnetworking device 300 onto a hard-to-reach location such as a pole, aradio tower, a wall, a stadium ceiling, etc.

FIG. 4 illustrates an angled view of the networking device 400 inaccordance with an embodiment. Specifically, the angled view reveals apatch panel section 402, and a patch panel 404 within patch panelsection 402. In some embodiments, networking device 400 can includepatch panel 404 at the bottom of networking device 400, facing downwardto prevent water from settling on patch panel 404.

Patch panel section 402 can include a set of cable-fastener loops (e.g.,loop 406), each loop comprising two openings along the surface of patchpanel section 402 and an inner compartment that guides a cable fastenerfrom one opening to the other.

Networking device 400 also includes a mounting bracket 406 that can beused to pole-mount the networking device, or to wall-mount thenetworking device. If networking device 400 is mounted on a pole of aradio tower, the network cables from patch panel 404 to the radioantennas can be kept at a minimum length, which minimizes the effects ofradio frequency (RF) interference, and reduces a likelihood that amalicious entity would tamper with networking device 400 and/or itsconnections to the radio antennas.

FIG. 5A illustrates a plurality of terminals accessible via a patchpanel 502 of networking device 500 in accordance with an embodiment.Patch panel 502 can include various terminals for receiving power, suchas a 24 V terminal block 506, a set of Power over Ethernet (PoE) inputports 508, or a 50V terminal block. PoE input ports 508 can receive 50 Vinput power, or can receive 24 V input power.

In some embodiments, a primary power supply can be coupled to any powerinput terminal of networking device 500, such as by coupling a highwattage power supply to 24 V terminal block 506 or the 50 V terminalblock, or by coupling a PoE adapter to a PoE input port 508. Moreover, abackup power supply can also be coupled to networking device 500, suchas via 24 V terminal block 506 or an available PoE input port 508. Forexample, the backup power supply can include a battery supply and/or asolar panel, which can provide power to networking device 500 in theoccasion that the primary power supply goes offline.

Patch panel 502 can also various terminals for sending and/or receivingdata, such as a console interface 504, Power over Ethernet (PoE) inputports 508, a set of 50 V PoE output ports 510, a set of 24 V PoE outputports 512, a serial modem interface port 514, and a set of fiber opticports 518. Serial modem interface port 514 can include a UniversalSerial Bus (USB) port for establishing a network connection with amodem. Also, fiber optic ports 518 can include a fiber optic port forreceiving data, and a second fiber optic port for sending data.

In some embodiments, console interface 504 can include any port forinterfacing networking device 500 with a terminal computer. For example,console interface 504 can include a serial port (e.g., an RS-232 port,an Ethernet port, a USB port, etc.), or a parallel port.

Also, in some embodiments, networking device 500 can receive a networkconnection and power via a Power over Fiber cable. For example, thePower over Fiber cable can include a power cable that can be coupled to24 V terminal block 506 or to the 50V terminal block, and can includetwo fiber optic cables (for full-duplex data transfer) that can becoupled to fiber optic ports 518.

FIG. 5B illustrates a conduit port 520 and a conduit adapter 522 ofnetworking device 500 in accordance with an embodiment. Conduit port caninclude a threaded inner surface which allows a conduit with matchingthreads at one end to be coupled to conduit port 520. In someembodiments, a conduit adapter 522 may be pre-installed into conduitport 520, such as to protect the threaded inner surface of conduit port520. If a custom electrical conduit is to be installed, a user canremove conduit adapter 522 from conduit port 520, and can install thecustom electrical conduit to conduit port 520. A set of cables can thenbe passed through the conduit and into the connector compartment ofnetworking device 500. However, if a custom conduit is not being used,conduit adapter 522 can be left coupled to conduit port 520.

When a front cover is installed to cover the connector compartment, thefront cover and the conduit can prevent contaminants from an outsideenvironment (e.g., water, dust, etc.) from entering into the connectorcompartment. The length of the custom conduit can be selected based onavailable space and the severity of the possible contaminants. Longerconduits can help prevent dust from entering into the connectorcompartment during strong winds, and can also prevent small rodents orbirds from entering and nesting inside the connector compartment.

For example, conduit port 520 can include a threaded opening with awidth and thread size that matches that of a standard pipe, such as aPVC pipe. Longer conduit pipes (e.g., 3 feet long or longer) candecrease the likelihood that water would enter into the connectorcompartment. A conduit pipe can also be used to prevent exposing cablesto outdoor elements by running the pipe down a tower and underground orinto a building or enclosure, such as to prevent the wires from beingtampered with or severed by people or animals. Some conduits may be madeof a rigid material (e.g., PVC, steel, copper, etc.). Other conduits maybe made of flexible material (e.g., a silicone or flexible plasticmaterial) that is easy for a technician to deploy around corners oralong surfaces with varying angles or elevation. If network device 500is used indoor, network device 500 can be mounted on a wall, and anangled conduit can be used to run the cables into the wall.

FIG. 5C illustrates an exemplary cable sleeve in accordance with anembodiment. Cable sleeve 530 can be made of weather-proof material thatcan prevent rain and dirt from entering into the connector compartmentof network device 500. Specifically, sleeve 530 can include a gasketalong one end, and an adjustable opening at an opposing end of sleeve530. A user can reduce the radius of the adjustable opening to decreasea spacing between the adjustable opening and a set of cables passingthrough the adjustable opening.

In some embodiments, the conduit adapter can mate with conduit port 520.For example, the user can pass gasket 532 through conduit adapter 522and into conduit port 520. Gasket 532 may rest against a side wall nextto the threads of conduit port 520, so that when the user insertsconduit port 522, conduit adapter can cause gasket 532 to press againstthe side wall. Once conduit port 522 is substantially fastened toconduit port 520 (e.g., by screwing the threads of conduit adapter 522along the threads of conduit port 520), gasket 532 and conduit adapter522 create a weather-resistant seal against the side wall of conduitport 520. In some embodiments, this weather-resistant seal may be ahermetic seal that can prevent rain from entering into the connectorcompartment.

In some embodiments, gasket 532 can be made of rubber (e.g., flexiblerubber, or hard rubber), or a stiff material (e.g., plastic, metal, asolid fibrous material, etc.), and may be embedded along the first endof sleeve 530. For example, gasket 532 may be held against sleeve 530 bya seam along the front end of sleeve 530. In a further embodiment, theseam can also be used to create a fold along the front end of sleeve 530(e.g., a pleat that folds sleeve material back upon itself). Thediameter of the front end and of the gasket may be sufficiently large toprovide a tight seal against the inner diameter of conduit port 520.

Sleeve 530 can include a sleeve tightener along a rear end (e.g., alongthe adjustable opening), which allows the user to adjust the radius ofthe adjustable opening. For example, the sleeve-tightener can include adrawstring 534 that can tighten the adjustable opening of sleeve 530.This allows the user to increase or decrease the number of cables thatrun through conduit port 520 and sleeve 530, without affecting thewaterproof abilities of sleeve 530. For example, a device that hasbreakaway ports may not allow the user to reseal a breakaway port onceit has been used (e.g., uncovered). The unused and uncovered breakawayports can leave an opening that is exposed to the external environmentthat may allow water to enter the connector compartment. If the userwould want to cover the breakaway port, the technician may need to use asealant to manually re-cover the breakaway port, which would require thetechnician to purchase the sealant, and could result in a messy sealthat would make it difficult to re-use the port in the future.

In some embodiments, sleeve 530 may be attached to conduit adapter 522.FIG. 5D illustrates an exemplary cable sleeve with a gasket adhered to aconduit adapter in accordance with an embodiment. Gasket 532 and one endof sleeve 530 may be adhered onto a front wall of conduit adapter 522,and the remainder of sleeve 530 may be passed through conduit adapter522. Then, when conduit adapter 522 is screwed fully into conduit port520, gasket 532 comes in contact with the side wall inside conduit port520 to make a weather-resistant seal.

In some embodiments, gasket 532 can include a cross-section shape thatcan contour around the side perimeter of conduit adapter 522 to improvethe seal between conduit adapter 522 and threaded port 520. For example,the cross-section shape can include an angled tube, so that one side ofthe angled tube is adhered to the front wall of conduit adapter 522.Also, the sleeve can be made of a water-resistant material, such as aneoprene material. In some embodiments, the sleeve's material can have asponge-like or foam-like characteristic, which can fill in gaps betweencables once the first end of the sleeve is tightened (e.g., using thesleeve-tightener).

FIG. 5E illustrates an exemplary cable sleeve coupled to a conduit portin accordance with an embodiment. Specifically, a set of cables 534 canpass through sleeve 530 and conduit port 520, and into a connectorcompartment of network device 500. For example, an Ethernet cable 540can be coupled to a PoE port of network device 500. Also, optical fibercable 542 can be passed through a strain-relief system that cansafeguard cable 542 from breaking, and one end of cable 542 can beinserted into an optical fiber connector. The strain-relief system caninclude a strain-relief arc 544 that prevents an edge of conduit port520 from breaking the optical fiber of cable 542, and can include aspool 546 for winding an unused length of cable prior to couplingoptical fiber cable 542 to the optical fiber port. Arc 544 and spool 546can each have a minimum radius that can prevent bending an optical fiberbeyond a predetermined maximum angle to prevent breaking the opticalfiber. In some embodiments, spool 546 can include a rubber band aroundits outer perimeter, which can prevent the optical fiber cable fromslipping, either while the cable is being wound around spool 546 orwhile the cable is kept wound around spool 546.

When an access cover is mounted onto network device 500 to cover theconnector compartment, the access cover becomes in contact with theouter perimeter of conduit port 520, without disrupting a set of cablespassing through conduit port 520. A user can also remove the accesscover without disturbing cables 538 that are connected to the portconnectors inside the connector compartment.

In some embodiments, sleeve 530 can be unfastened along one side tounwrap from cables 538, such as by undoing a fastener along the side.This can provide a simple way to remove sleeve 530 without having todisconnect cables 538 from their respective ports. Moreover, if sleeve530 is to be installed at a later time, sleeve 530 can be wrapped aroundcables 538, and then fastened along one side to form an enclosure aroundthe cables. Sleeve 530 can then be inserted into conduit port 520,followed by inserting and fastening conduit adapter 522 into the conduitport.

FIG. 5F illustrates an exemplary cable sleeve being wrapped or unwrappedfrom a set of cables in accordance with an embodiment. The sleeve's sidefastener can be made of bonded zippers with weatherproof edging, or canbe made of a hook-and-loop fastener (e.g., Velcro), or anywater-resistant reversible fastener now known or later developed. Also,gasket 532 can be open-ended, so that when the sleeve's fastener isclosed, gasket 532 also becomes closed to form a loop with tightwater-resistant contact between the two ends. In some embodiments, thesleeve-tightener may include a cordlock 536, or any type of removabledrawstring fastener now known or later developed. Two ends of drawstring534 can be inserted into cordlock 536 to tighten the distal end ofsleeve 530. Also, the two ends of drawstring 534 can be removed fromcordlock 536 when the sleeve's side fastener is undone to completelyunwrap and remove sleeve 530 from a set of cables.

In some embodiments, instead of or in addition to having a sleeve,conduit adapter 522 can include a membrane with a center gap or hole forpassing a set of cables. FIG. 5G illustrates an exemplary conduitadapter 522 with a membrane 540 at a distal end in accordance with anembodiment. The user can create a gap 542 with a gap size thataccommodates the number of cables that are to be passed through theconduit adapter, without leaving a significant amount of additionalempty space between gap 542 and the cables. For example, membrane 540can be on the distal end or on the proximal end of conduit adapter 522.Also, gap 542 may initially have a size suitable for passing one or morecables, but may be made larger (e.g., by cutting membrane 540 to extendgap 542) as additional cables are passed through membrane 540.

In a further embodiment, a technician may also insert a sealant intoconduit adapter 522 to seal gaps between the cables and the inner wallsof conduit adapter 522. The sealant may be used in addition to sleeve530 and/or membrane 540, such as by inserting the sealant into conduitadapter 522 from inside the connector compartment (e.g., from theproximal end of conduit port 520). If a sleeve is used along withconduit adapter 522, the sealant may rest on a top surface of the sleeve(e.g., the inner sleeve surface), so that the sleeve behaves as a cupfor the sealant. Alternatively, if the distal end of conduit adapter 522comprises a membrane, the sealant may rest on a top surface of themembrane. In some embodiments, the sealant may include a non-conductivefoam or gel, such as a silicone-based foam or gel.

FIG. 6A illustrates a mounting bracket 604 of the networking device 600in accordance with an embodiment. Mounting bracket 604 can be used tomount the networking device on a pole or on a wall surface. Whenmounting the networking device on a pole or wall surface, the user canfirst install mounting bracket 604 to the desired surface. Then, theuser can insert rails 602 of networking device 600 into mounting bracket604.

Mounting bracket 604 can include a set of mounting holes (e.g., hole616) for fastening mounting bracket 604 to a wall surface using a set ofscrews. Mounting bracket 604 can also include a curved surface 618,which facilitates fastening mounting bracket 604 to a pole. For example,the user can place mounting bracket 604 against a pole so that the poleis pressed against curved surface 618, and can fasten a secondpole-mounting bracket (not shown) to mounting bracket 604 by insertingand tightening a set of bolts against the mounting holes.

In some embodiments, networking device 600 can include a bracket lockingmechanism that can fasten and lock mounting bracket 604 to networkingdevice 600. For example, the user can insert screws from insidenetworking device 600, which fasten mounting bracket 604 to networkingdevice 600. To remove networking device 600 from mounting bracket 604,the user needs to remove a front panel 620 from networking device 600,unscrew and remove the screws from within the connector compartment, andslide networking device 600 along direction 622.

In some embodiments, front panel 620 can be fastened to a rear chassisof networking device 600 by a locking mechanism 624, such as a screw. Ifthe user wants to gain access to the patch panel or to unmountnetworking device from mounting bracket 604, the user needs to firstremove front panel 620 by disengaging (e.g., unscrewing) lockingmechanism 624.

FIG. 6B illustrates a set of rails 602 of networking device 600partially inserted into mounting bracket 604 in accordance with anembodiment. Specifically, rails 602 can slide into mounting bracket 604until rails 602 make contact with a side wall 606 of mounting bracket604.

FIG. 7 illustrates a set of cable-fastener loops 702.1 and 702.2 on acompartment surface 704 of networking device 700 in accordance with anembodiment. Specifically, cable-fastener loop 702.1 can includes twoopenings for looping a cable fastener (e.g., a cable tie) into a firstopening and out of a second opening of cable-fastener loop 702.1. Also,cable-fastener loop 702.1 can include a curved surface underneath thetwo openings, which guides the cable fastener from one opening to theother opening.

FIG. 8 illustrates curved surfaces 802.1 and 802.2 underneath thecable-fastener loops of networking device 800 in accordance with anembodiment. The curved surfaces reside below the compartment surface ofnetworking deice 800, so that each curved surface is below a pair ofopenings that form a cable-fastener loop on the compartment surface.Specifically, a curved surface 802.1 can guide a cable fastener from oneopening of a cable-fastener loop to a neighboring opening.

FIG. 9A illustrates a networking device 900 exposing a multiple heatpipe configuration in accordance with an embodiment. Specifically, themultiple heat pipe configuration can include a heat pipe 906.1 coupledto a heat sink 912, as well as a second heat pipe 906.2 coupled to thesame heat sink 912. Each heat pipe can include a plate at one end (e.g.,plate 908.2) that sources heat from a heat source (e.g., a circuitelement), and includes a plate at an opposing end of the heat pipe(e.g., plate 910.2) that dissipates the heat to heat sink 912. In someembodiments, the heat source can include a communications microchip, amicroprocessor, a power transistor, and/or a signal-amplifyingmicrochip. Moreover, in some embodiments, networking device 900 caninclude a network router.

The heat pipe can include a tube comprising a thermally conductivesurface, and filled with a fluid that transfers heat along the heatpipe. The heat pipe channels heat from the heat source to heat sink 912as the fluid evaporates when heated by the heat source and condenseswhen cooled by the heat sink. Also, heat sink 912 can be oriented at atop portion of networking device 900, and in close proximity to a set ofheat-dissipating fins 916 along a front chassis of networking device900. The top orientation of heat sink 912 can dissipate heat from a heatsource that travels upward via the heat pipe coupled to the heat source.Similarly, the top orientation of heat-dissipating fins 916 candissipate heat from the heat source, which is transferred upward towardthe top of networking device 900 by the air inside networking device900.

In some embodiments, heat sink 912 can include a set of screw holes formounting an additional heat pipe. The additional heat pipe can transferheat from an existing heat source of networking device 900, or from aheat source that is added to networking device 900 at a later time.

FIG. 9B illustrates an angled side view of the heat pipes 906.1 and906.2 mounted on heat sink 912 of networking device 900 in accordancewith an embodiment. Specifically, heat pipe 906.1 can include a plate908.1 pressed against heat source (not shown) by a spring screw 904.1,and includes a plate 910.1 pressed against heat sink 912 by springscrews 918.1 and 918.2. Heat sink 912 can include any thermal-conductivematerial, such as aluminum.

In some embodiments, a spring screw may include a screw that can betightened into a standoff on the networking device's motherboard. Thespring screw may also include a coil spring which can push against thescrew head and plate 908.1 when the screw is screwed into and tightenedin the standoff. The standoff can produce a consistent distance betweenthe screw's head and the motherboard. Given that the distance from thescrew head and the motherboard is constant, the force at which plate908.1 presses against the heat source is governed by the force exertedby the compression coil spring used in spring screw 904.1.

In some embodiments, plate 908.1 of heat pipe 906.1 may be pressedagainst the heat source by a screw without a spring, and plate 910.1 ofheat pipe 906.1 may be pressed against heat sink 912 by additionalscrews without springs.

FIG. 10 illustrates a networking device 1000 exposing a single heat pipeconfiguration in accordance with an embodiment. Specifically, the heatpipe configuration can include a heat pipe 1002 coupled to a heat sink1004. Heat pipe 1002 can include a curved shape that runs near a portionof a perimeter of a heat source to increase the thermal contact betweenheat pipe 1002 and the heat source. The increased thermal contact canimprove the efficiency at which heat pipe 1002 moves heat away from theheat source, and onto heat sink 1004. In some embodiments, the heatsource can include a communications microchip, a microprocessor, a powertransistor, and/or a signal-amplifying microchip. Moreover, networkingdevice 1000 can include a network switch.

In some embodiments, the rear chassis section of the networking devicecan include a set of heat-dissipating fins, which can be in thermalcontact with a heat sink inside the networking device. Theheat-dissipating fins can transfer heat away from the heat sink and ontoan environment external to the networking device.

FIG. 11 illustrates a set of heat-dissipating fins 1102 of a networkingdevice 1100 in accordance with an embodiment. Heat-dissipating fins 1102are oriented along a top portion of networking device 1100, on a rearchassis section of networking device 1100. Heat-dissipating fins 1102may be in thermal contact with a heat sink of networking device 1100,and can transfer heat away from the heat sink onto an environmentexternal to networking device 1100.

Specifically, heat-dissipating fins 1102 may not include vent openingsthat would dissipate air from inside of networking device 1100. Rather,heat-dissipating fins 1102 include interdigitating sections of surfacearea that are elevated (or suppressed) relative to its two neighboringsections of surface area. Hence, heat-dissipating fins 1102 provideadditional surface area that improves the transfer of heat to anenvironment external to networking device 1100.

FIG. 12 illustrates a close-up angled view of heat-dissipating fins 1202on a rear surface of a networking device 1200 in accordance with anembodiment. FIG. 12 also illustrates another set of heat-dissipatingfins 1204 on a front surface of networking device 1200. In someembodiments, heat-dissipating fins 1202 and 1204 may each besubstantially parallel to a heat sink inside networking device 1200, andat opposing sides of the heat sink. For example, heat-dissipating fins1202 and 1204, as well as the heat sink, may reside on a top section ofnetworking device, which allows heat to rise toward the heat sink and toheat-dissipating fins 1202 and 1204. Heat-dissipating fins 1202 may bein thermal contact with the heat sink, and may dissipate heat away fromthe heat sink via the thermal contact. Heat-dissipating fins 1204, onthe other hand, may dissipate heat away from the heated air inside a topsection of networking device 1200.

Mini Networking Device

In some embodiments, the networking device can be implemented in a smallform factor for radio towers that include a few low-power antennas.

FIG. 13 illustrates a front-chassis 1300 for a low-power networkingdevice in accordance with an embodiment. Specifically, front-chassis1300 is coupled to a rear chassis (not shown) to house a printed circuitboard (PCB) chamber. Front-chassis 1300 is resistant to weatherintrusion to protect the cable connectors and the internal electronicsfrom various weather phenomena such as rain, snow, and sun heat.

Front chassis 1300 includes a patch panel section 1302 at a bottomsection of front chassis 1300 to prevent water or rain from coming incontact with and settling on a set of cable connectors. In someembodiments, front chassis 1300 for the low-power networking device doesnot need to include a vent or a set of heat-dissipating fins todissipate heat from inside the PCB chamber of the networking device.Front chassis 1300 can include a set of light-emitting diodes (LEDs)1304 that each indicates a status (e.g., a link status, a power status,etc.), and includes a logo 1306 (e.g., a manufacturer logo, or a productlogo). For example, a subset of LEDs 1304 can be arranged in a row ofLED pairs, where a respective LED pair indicates a transmit status andreceive status for a link.

Patch panel section 1302 can include a set of cable-fastener loops(e.g., loop 1310), each loop comprising two openings along the surfaceof patch panel section 1302 and an inner compartment that guides a cablefastener from one opening to the other. Patch panel section 1302 alsoincludes a cover-fastener hole 1308 for fastening a patch panel cover topatch panel section 1302. Specifically, the patch panel cover caninclude a pin that fastens to the networking device chassis wheninserted into cover-fastener hole 1308.

FIG. 14 illustrates a patch panel 1402 of a low-power networking device1400 in accordance with an embodiment. Patch panel 1402 of networkingdevice 1400 can include various terminals for receiving power, such as a24 V terminal block 1404, a set of Power over Ethernet (PoE) ports 1406and 1408, and a USB port 1410.

In some embodiments, edge server 1400 can receive power via a PoE port1406. Hence, a primary power supply and a backup power supply can becoupled to any power input terminal of networking device 1400, such asby coupling a high wattage power supply to 24 V terminal block 1404,and/or by coupling a PoE adapter to PoE port 1406.

Moreover, PoE ports 1408 can be used to send and/or receive data. Forexample, one port of PoE ports 1406 or 1408 can be coupled to anInternet service provider (ISP), and one or more additional PoE ports1408 can each be coupled to an antenna to relay a network connection toa remote station.

FIG. 15 illustrates a pole-mount feature 1502 of a low-power networkingdevice 1500 in accordance with an embodiment. Specifically, pole-mountfeature 1502 includes a set of vertically aligned protrusions that mayextend above the surface of networking device 1500. The set ofprotrusions can have varying heights to form a curved shape that cancontour a pole's curved surface.

FIG. 16 illustrates a curved contour of a pole-mount feature 1602 inaccordance with an embodiment. Specifically, a rear chassis of anetworking device 1600 can include a rear flat surface, and can includea pole-mount feature 1602 that extends beyond the rear flat surface.

Pole-mount feature 1602 can have a curved shape that may contour apole's curved surface. Pole-mount feature 1602 can also include rails1604 and 1606 at opposing sides of pole-mount feature 1602. Rails 1604and 1606 facilitate attaching a wall-mount attachment (not shown) overpole-mount feature 1602 by sliding the wall-mount attachment along rails1604 and 1606. For example, a user can install the wall-mount attachmentonto networking device 1600 by sliding rails 1604 and 1606 intocorresponding slots of the wall-mount attachment in a vertical direction(e.g., in a downward direction), until rails 1604 and 1606 reach afastened position within the wall-mount attachment. In some embodiments,rails 1604 and 1606 reach a fastened position when they make contactwith a bottom portion of the wall-mount attachment.

FIG. 17 illustrates a PCB compartment 1702 of a low-power networkingdevice 1700 in accordance with an embodiment. Networking device 1700does not include vents between compartment 1702 and the externalenvironment, which protects circuits within compartment 1702 from theexternal environment, such as from dust, rain, and other weatherphenomenon. Rather, networking device 1700 can include a heat radiator1706 that radiates heat away from a motherboard, and onto the chassis ofnetworking device 1700. The heat can radiate away from the chassis tothe external environment. PCB compartment 1702 can also include a lightpipe assembly 1704, which can include a set of light emitting diodes(LEDs) without allowing a significant amount of light to bleed betweenneighboring LEDs.

FIG. 18 illustrates a cover plate 1802 of a networking device 1800 inaccordance with an embodiment. For illustration purposes, cover plate1802 is shown as a transparent line drawing to reveal a connector paneland a set of cable-fastening loops. Specifically, cover plate 1802covers a patch panel, and can include a set of cable holes that are eachcovered with a breakaway cover (e.g., breakaway cover 1804). When theuser needs to run a cable through a hole of cover plate 1802, the usercan remove the breakaway cover that covers the cable hole. The user canfasten one or more cables to a cable-fastening loop (e.g.,cable-fastening loop 1806) by running a fastener (e.g., a cable tie)through the cable-fastening loop, and fastening the fastener around theone or more cables.

Hence, fastening a set of cables to the cable-fastener loops (e.g.,using cable ties) effectively aligns these cables to the cable holes ofcover plate 1802. This makes it easier for the user to install coverplate 1802 back onto networking device 1800, as the cables remainaligned to the cable holes of cover plate 1802 with little or noadditional effort required by the user to re-align the cables to thecable holes while installing cover plate 1802.

FIG. 19 illustrates an exemplary light pipe assembly 1900 of anetworking device in accordance with an embodiment. Light pipe assembly1900 includes two rows of light pipes. Each light pipe can include anLED within a slot of the light pipe, such that the light pipe preventslight from a rear portion of the LED from escaping to a neighboring LED.Hence, light pipe assembly 1900 can reduce or eliminate an amount oflight that bleeds between neighboring LEDs.

Cloud-Based Management of Remote Stations

Embodiments of the present invention also provide a cloud-basedcontroller that allows a technician to determine the status of aplurality of networking devices deployed over a wide area. The cloudcontroller can ping each of the deployed networking devices to determineits status, and can present this status information to the user in aunified UI. In some embodiments, the cloud controller can include acomputer cluster that manages a plurality of networking devices for anentity (e.g., an ISP, or a company with a closed network), or formultiple entities.

The cloud controller can get location information from each networkingdevice, and can display the location of each networking device on a map,along with icons that each represents a current status of acorresponding networking device. The cloud controller can communicatewith various networking devices remotely to keep track of their statusand configuration, and can present this diagnostic information to thetechnician via the unified UI so that the technician does not need todiagnose a radio tower in-person. For example, the cloud controller canpresent diagnostic information for a networking device on a map UI. Thediagnostic information can include a configuration of the networkingdevice, performance information (e.g., throughput information),information on the radios or antennas coupled to the networking device,information on one or more power sources, etc.

The cloud controller can also provide a device-specific UI that displaysstatus information and configuration options for a given networkingdevice, such as which antennas are coupled to the networking device, thesignal quality and bandwidth of each antenna, etc. This device-specificUI allows the technician to perform a detailed analysis of a givennetworking device, for example, to determine whether a given radio towerneeds servicing, for example, to determine whether a given networkingdevice or antenna needs to be repaired or replaced, etc.

FIG. 20 presents a flow chart illustrating a method 2000 for managing aset of networking devices from a remote cloud controller in accordancewith an embodiment. During operation, the cloud controller can receive arequest from a client device to monitor one or more networking devices(operation 2002), and determines a set of radios coupled to a respectivenetworking device (operation 2004). The cloud controller then generatesa user interface (UI) that overlays device icons for the one or morenetworking devices over a map of a geographic region (operation 2006).

In some embodiments, the UI can display status information for eachnetworking device (e.g., in the device icon, or next to the deviceicon). The status information can include, for example, a networkthroughput for a predetermined network port of the networking device, asignal strength for a predetermined radio, an aggregate signal strengthfor one or more radios, and an average signal strength for one or moreradios.

In some embodiments, the cloud controller can receive a user input fromthe client device (operation 2008), and analyzes the user input todetermine a type of input that was submitted (operation 2010). The userinput can be a map UI navigation input that selects a new geographicregion to display in the map UI, in which case the cloud controllerupdates the map UI to display networking devices associated with the newgeographic region (2012).

The user input can also be a device icon selection, which selects anetworking device to monitor, in which case the cloud controller updatesthe UI to present detailed information on the selected networking device(operation 2014). The detailed information can include, for example, aconfiguration for one or more components of the networking device,and/or an operating state for the one or more components of thenetworking device. The detailed information can also include an alertassociated with a misconfigured, underperforming, or malfunctioningcomponents of the networking device, and/or a diagnosis associated withthe alert.

In some embodiments, the user input can be a device configuration for auser-selected networking device, in which case the cloud controllerconfigures the selected networking device based on the deviceconfiguration (operation 2016).

FIG. 21 illustrates an exemplary computer system 2102 that facilitatesmanaging a set of networking devices in accordance with an embodiment.Computer system 2102 includes a processor 2104, a memory 2106, and astorage device 2108. Memory 2106 can include a volatile memory (e.g.,RAM) that serves as a managed memory, and can be used to store one ormore memory pools. Furthermore, computer system 2102 can be coupled to adisplay device 2110, a keyboard 2112, and a pointing device 2114.Storage device 2108 can store operating system 2116, a router-managingsystem 2118, and data 2128.

Router-managing system 2118 can include instructions, which whenexecuted by computer system 2102, can cause computer system 2102 toperform methods and/or processes described in this disclosure.Specifically, router-managing system 2118 may include instructions forreceiving router-managing requests from a client device (communicationmodule 2120), and may include instructions for processing a request fromthe client device (input-processing module 2122). Further,router-managing system 2118 can include instructions for generating orupdating a UI to present status information for a plurality ofnetworking devices over a map of a geographic region (UI-generatingmodule 2124). Router-managing system 2118 can also include instructionsfor configuring one or more networking devices based on a configurationreceived in a request from the client device (router-configuring module2126).

Data 2128 can include any data that is required as input or that isgenerated as output by the methods and/or processes described in thisdisclosure.

The data structures and code described in this detailed description aretypically stored on a computer-readable storage medium, which may be anydevice or medium that can store code and/or data for use by a computersystem. The computer-readable storage medium includes, but is notlimited to, volatile memory, non-volatile memory, magnetic and opticalstorage devices such as disk drives, magnetic tape, CDs (compact discs),DVDs (digital versatile discs or digital video discs), or other mediacapable of storing computer-readable media now known or later developed.

The methods and processes described in the detailed description sectioncan be embodied as code and/or data, which can be stored in acomputer-readable storage medium as described above. When a computersystem reads and executes the code and/or data stored on thecomputer-readable storage medium, the computer system performs themethods and processes embodied as data structures and code and storedwithin the computer-readable storage medium.

Furthermore, the methods and processes described above can be includedin hardware modules. For example, the hardware modules can include, butare not limited to, application-specific integrated circuit (ASIC)chips, field-programmable gate arrays (FPGAs), and otherprogrammable-logic devices now known or later developed. When thehardware modules are activated, the hardware modules perform the methodsand processes included within the hardware modules.

The foregoing descriptions of embodiments of the present invention havebeen presented for purposes of illustration and description only. Theyare not intended to be exhaustive or to limit the present invention tothe forms disclosed. Accordingly, many modifications and variations willbe apparent to practitioners skilled in the art. Additionally, the abovedisclosure is not intended to limit the present invention. The scope ofthe present invention is defined by the appended claims.

What is claimed is:
 1. A tower-mounted networking device, comprising: apoint-to-point radio configured to establish a point-to-point wirelesscommunication with a remote point-to-point radio in a remote networkingdevice; a point-to-multipoint radio configured to establish respectivewireless communications with a plurality of user devices; a first portconfigured to receive power from a power source to power the networkingdevice and data from a wired communication; and forwarding circuitryconfigured to: receive a packet via the point-to-point wirelesscommunication from the remote networking device; and forward the packetto a user device of the plurality of user devices via a correspondingwireless communication using the point-to-multipoint radio.
 2. Thenetworking device of claim 1, further comprising a second point-to-pointradio configured to establish a second point-to-point wirelesscommunication with a second remote point-to-point radio in a secondremote networking device.
 3. The networking device of claim 2, whereinthe forwarding circuitry is further configured to forward a secondpacket, which is received via the second point-to-point radio from thesecond remote networking device, to the remote networking device via thepoint-to-point wireless communication.
 4. The networking device of claim1, further comprising a second port capable of receiving power, whereinthe first port is a primary power source, and wherein the second port isa secondary power source.
 5. The networking device of claim 1, whereinthe point-to-multipoint radio is a cellular radio, and wherein arespective user device of the plurality of user devices is equipped witha cellular radio that establishes the communication with thepoint-to-multipoint radio.
 6. The networking device of claim 1, whereinthe point-to-multipoint radio is a WiFi radio, and wherein a respectiveuser device of the plurality of user devices is equipped with a WiFiradio that establishes the communication with the point-to-multipointradio.
 7. The networking device of claim 1, further comprising a chassiscomprising a weather-resistant printed circuit board (PCB) chambercapable of resisting weather intrusion, wherein the chassis is capableof dissipating heat away from high-power electronics of an internal PCBin the PCB chamber without requiring ventilation ports on the chassis.8. The networking device of claim 1, the first port includes one of: aPower-over-Ethernet (PoE) network port and a Power-over-Fiber networkport.
 9. The networking device of claim 1, further comprising acontroller configured to: receive a configuration instruction via thepoint-to-point radio or the point-to-multipoint radio; and configure thenetworking device based on the configuration instruction.
 10. Thenetworking device of claim 1, wherein the first port is configured toreceive the power from the power source and the data from the wiredcommunication from a single external cable coupled to the first port.11. A computer system mounted on a radio tower or wall, comprising: aprocessor; a plurality of radios; a first port configured to receivepower from a power source to power the computer system; and a memorycoupled to the processor and storing instructions, which when executedby the processor cause the processor to perform a method, the methodcomprising: establishing, via a point-to-point radio of the plurality ofradios, a point-to-point wireless communication with a remotepoint-to-point radio in a remote networking device; establishing, via apoint-to-multipoint radio of the plurality of radios, respectivewireless communications with a plurality of user devices; receiving, viathe point-to-point wireless communication, a packet from the remotenetworking device; and forwarding the packet to a user device of theplurality of user devices via a corresponding wireless communicationusing the point-to-multipoint radio.
 12. The computer system of claim11, wherein the method further comprises establishing, via a secondpoint-to-point radio of the plurality of radios, a second point-to-pointwireless communication with a second remote point-to-point radio in asecond remote networking device.
 13. The computer system of claim 12,wherein the method further comprises forwarding a second packet, whichis received via the second point-to-point radio from the second remotenetworking device, to the remote networking device via thepoint-to-point wireless communication.
 14. The computer system of claim11, further comprising a second port capable of receiving power; whereinthe method further comprises selecting the first port as a primary powersource and the second port as a secondary power source.
 15. The computersystem of claim 11, wherein the point-to-multipoint radio is a cellularradio, and wherein a respective user device of the plurality of userdevices is equipped with a cellular radio that establishes thecommunication with the point-to-multipoint radio.
 16. The computersystem of claim 11, wherein the point-to-multipoint radio is a WiFiradio, and wherein a respective user device of the plurality of userdevices is equipped with a WiFi radio that establishes the communicationwith the point-to-multipoint radio.
 17. The computer system of claim 11,further comprising a chassis comprising a weather-resistant printedcircuit board (PCB) chamber capable of resisting weather intrusion,wherein the chassis is capable of dissipating heat away from high-powerelectronics of an internal PCB in the PCB chamber without requiringventilation ports on the chassis.
 18. The computer system of claim 11,the first port includes one of: a Power-over-Ethernet (PoE) network portand a Power-over-Fiber network port.
 19. The computer system of claim11, wherein the method further comprises: receiving a configurationinstruction via the point-to-point radio or the point-to-multipointradio; and configuring the computer system based on the configurationinstruction.
 20. The computer system of claim 11, wherein the first portis configured to receive the power from the power source from a singleexternal cable coupled to the first port; and wherein the method furthercomprises receiving the data from the wired communication from theexternal cable.